home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
FishMarket 1.0
/
FishMarket v1.0.iso
/
fishies
/
476-500
/
disk_479
/
uucp
/
newssetup.doc
< prev
next >
Wrap
Text File
|
1992-05-06
|
7KB
|
158 lines
NEWSSETUP.DOC
AS OF UUCP VERSION 1.07, NEWS WORKS DIFFERENTLY. There is no longer a
'NewsFeed' configuration entry. Instead, there is a new file called
UULIB:SYS which contains a list of upstream and downstream news sites.
ANEWS IS NOW COMPLETELT OBSOLETE, HENCE THE BINARY IS NOT IN UUCP:C,
YOU MUST USE DNEWS.
To maintain compatibility with older UUCP's, if the NewsFeed
configuration entry still exists and UULIB:Seq does *not* exist, then
postnews will create a UULIB:Seq file containing an entry for the
NewsFeed. Additionally, if the NewsFeed configuration entry still
exists, postnews will automatically run batchnews after queueing the
news.
To use the new news system with one or more upstream or downstream
sites (upstream sites feed you, you feed downstream sites), you should
create a UULIB:Seq file (refer to the 'Sys' manual page) containing the
site or sites in question and DELETE the 'NewsFeed' CONFIG ENTRY. The
direct translation of the old 'NewsFeed' config entry is a line in
the UULIB:Sys file that reads:
newsfeed:* <- note, only the machine name, not a full
domain name.
Now you have a choice. You can either have BATCHNEWS run automatically
whenever you post news, or you can run BATCHNEWS as an option to UUCico,
or you can run BATCHNEWS from your CRONTAB, or you can run BATCHNEWS
manually.
(1) If you have only a single upstream newsfeed and do not post all
that much news, then you can have BatchNews run automatically
by PostNews by adding a config entry to UULIB:Config :
AutoBatch autobatch
(2) If you have only a single upstream newsfeed and post a lot of
news AND you call out to your news (verses it calling you)
most of the time, the easiest thing to do is to specify the
-b option to UUCico when calling out. This forces all queued
articles to be batched before UUCico makes its telephone call.
Do NOT use the AutoBatch config entry
Do NOT use the -b option for UUCico's run from PASSWD (i.e.
receiving a call)
(3) If you have a single upstream newsfeed and post a lot of news
and the feed site calls you most of the time, then you do NOT
want to specify -b in the uucico in the Passwd file because
it may take a while to compress your news and this can shoot
your telephone bill up... the remote site may even hang up.
Instead, I suggest adding a DCron CRONTAB entry to
automatically batch your news at regular intervals (or, if you
know when the system is to call you, half an hour or so before
they call you). Then when the system calls, the news will
already be pre-batched and waiting in spool for immediate
transfer.
Do NOT use the AutoBatch config entry
Do NOT use the -b option for UUCico's run from PASSWD (i.e.
receiving a call)
(4) If you have an upstream feed and also feed news to multiple
downstream sites then you want to, again, use a DCron CRONTAB
entry to automatically batch all pending news at regular
intervals, since the assumption is that you are both calling
out and other machines are calling you. You do NOT want to
specify the -b option to UUCico for the same reasons as (3)...
in this case the results might even be worse!
Do NOT use the AutoBatch config entry
Do NOT use the -b option for UUCico's run from PASSWD (i.e.
receiving a call)
NOTE: If the old NewsFeed config entry exists and the Sys file does
not exist, PostNews will automatically send a warning to
the postmaster (i.e. you if you set up your UULIB:Aliases
correctly) and create a Sys file. If the old NewsFeed config
entry exists and a sys file exists PostNews will ignore the
old Newsfeed config entry but will silently enable AutoBatch
so dummies who do not set up their system correctly can still
post news. Do not rely on this silent AutoBatch enable, please
use the new AutoBatch config entry if you wish AutoBatching.
NOTE: BATCHNEWS does not take much cpu when no news needs to be batched
and can safely be run in small intervals.
The program 'DNews', may be used to read news. Before 1.06D the
program was ANews. ANews source is included in 1.07 but is no longer
usable to post news and so the binary is not included. News is placed
in separate directories in the UUNEWS: directory.
As I said, really aweful documentation eh?
---
WHERE DOES NEWS GO?
News goes into UUNEWS: unless you overide it with a Config entry
like this:
UUNews barf:somedirectory
If you leave it at UUNEWS: then you must make sure UUNEWS: is
Assign'd to the appropriate directory. The Assign is normally
done from your startup-sequence.
Before 1.07 you needed to specify a feed site via the NewsFeed
configuration entry. This is NO LONGER USED, though some compatibility
is maintained for those who do not read this document. Note that the
configuration entry will be completely phased out in 1.08. The new
place for the news feed configuration is in the UULIB:Sys file
---
WHAT NEWSGROUPS DO I GET
You get the newsgroups your feed sends you (you have to tell them what
you want), and you must also list the groups in the file
UULIB:NewsGroups . Any newsgroups you receive that are not in
UULIB:NewsGroups is placed into the UUNEWS:Junk directory.
If you intend to propogate news to other sites and have their news
propogated back through you, any news not listed in UULIB:NewsGroups
will be placed in UUNEWS:Junk, BUT STILL PROPOGATED. This allows
downstream sites to post news to groups you do not normally receive and
vise-versa. If you wish to prevent news propogation of newsgroups not
listed in UULIB:NewsGroups, you can clear out the Junk directory before
running BatchNews, or perhaps use the TrimNews program to radically
lower the amount of time messages in Junk stick around.
---
HOW IS NEWS TRANSFERED
News is transfered by UUCP. Your feed site will send you the news
compressed. It will be run through the RNews program which
automatically uncompresses it and splits it up into separate articles,
creating any necessary directories, and placing said articles in those
directories according to the newsgroups each article is destined for.
When you post news (via DNews), your UULIB:Sys file determines which
sites are to receive the news. No site that the news has already
propogated through will ever receive the news. The article is queued
by appending the file path to the article to the appropriate
file UUSPOOL:BATCH/<system>. Then, when BATCHNEWS is run all files
in UUSPOOL:BATCH are scanned, the articles extracted, compressed, and
queued to UUSPOOL: for UUCP transfer.
---
READING NEWS WITH DNEWS
POSTING NEWS
REFER TO man/DNews